Computer system preventing storage of duplicate files

ABSTRACT

Arrangements including a duplication determination unit that determines whether identical contents intrinsic values are contained in a plurality of contents intrinsic values; a change control unit that changes an access destination of a first file corresponding to a first contents intrinsic value from identical contents intrinsic values, to a position having stored therein a second file corresponding to a second contents intrinsic value from among these identical contents intrinsic values when there are identical contents intrinsic values; and, a migration execution unit which, when the migration execution unit migrates data stored in files stored in one or more first logical storage devices to one or more second logical storage devices, does not migrate first data of the first file to any of the one or more second logical storage devices, and migrates second data of the second file to any of the one or more second logical storage devices.

CROSS-REFERENCE TO PRIOR APPLICATION

This is a continuation of U.S. application Ser. No. 11/972,659, filedJan. 11, 2008 now U.S. Pat. No. 7,900,000. This application relates toand claims priority from Japanese Patent Application No. 2007-082052,filed on Mar. 27, 2007. The entirety of the contents and subject matterof all of the above is incorporated herein by reference.

BACKGROUND

The present invention relates to a storage control technology ofelectronic files.

For example, a NAS (Network Attached Storage) node (for example, a fileserver) manages the file, and the body of the file is stored in astorage device inside the NAS node or outside the NAS node.

Generally the files with different names are stored in a storage deviceeven if the file contents is the same. In this case, the files withabsolutely identical contents (that is, the files with completelyduplicate contents) are stored in the storage device. Therefore, thestorage capacity is unnecessarily consumed. The technologies disclosedin Japanese Patent Applications Laid-open No. 2005-235171 and2005-174339 are examples of storage control technologies for preventingthe storage of duplicate files. For example, the following is disclosedin Japanese Patent Applications Laid-open No. 2005-235171 and2005-174339.

There are present a host and a storage device. The host has anapplication and a special API (Application Program Interface). Thestorage device communicates with the special API. When the API of thehost receives a file storage request from the application, if theassociation of the file name of the file and the below-describedcontents address is not managed, the file is transmitted to the storagedevice, but if the association is managed, the contents address of thefile is transmitted to the storage device. When the storage devicereceives the file from the API of the host, a hash value is generatedfrom the file contents. This hash value is the contents address. Thestorage device stores the received file, performs management byassociating the generated contents address with the physical storagelocation of the file, and returns the contents address to the API of thehost. The API of the host performs management by associating thecontents address received from the storage device with the file name ofthe transmitted file. On the other hand, when the storage devicereceives the contents address from the API of the host, the storagedevice acquires the file from the physical storage location associatedwith the contents address and returns the acquired file to the API ofthe host.

With the technology disclosed in Japanese Patent Applications Laid-openNo. 2005-235171 and 2005-174339, a hash value generated in the storagedevice is used as a contents address. Therefore, a special API of ahigh-level device such as a host is necessary to designate the file withthe contents address to the storage device.

SUMMARY

It is an object of the present invention to prevent the storage ofduplicate files even when a special API is not required for a high-leveldevice.

Other objects of the present invention will become clear from thefollowing description.

A plurality of contents intrinsic values that are values intrinsic torespective contents of a plurality of files stored in one or more firststorage devices are calculated. Whether two or more identical contentsintrinsic values are contained in said plurality of contents intrinsicvalues is determined. When two or more identical contents intrinsicvalues are present, an access destination of a first file correspondingto a first contents intrinsic value from among these two or morecontents intrinsic values is changed to a position having stored thereina second file corresponding to a second contents intrinsic value fromamong these two or more contents intrinsic values.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block-diagram illustrating a configuration example of acomputer system of the first embodiment of the present invention;

FIG. 2A shows an example of a computer program executed by a CPU locatedinside a controller unit of the primary storage system;

FIG. 2B shows a configuration example of an Address Map ManagementTable;

FIG. 2C shows a configuration example of an LDEV Management Table;

FIG. 3 shows a configuration example of a management terminal;

FIG. 4 illustrates information collection from an NAS node and a primarystorage system;

FIG. 5 shows an example of a Directory File Information Table that ismanaged by a File System Program of a NAS node;

FIG. 6 shows a table having recorded therein information relating to alogical volume storing a file or a directory and a portion of a LDEVManagement Table managed by a primary storage system;

FIG. 7 shows a configuration example of a Contents Identifier ManagementTable;

FIG. 8 shows in general a flow of processing performed in the computersystem of the first embodiment;

FIG. 9 shows how an access attribution “Read Only” is set in theinternal LDEV of an archive object in S101 of FIG. 8;

FIG. 10 shows how a Contents Identifier Management Table is created andtransmitted to a primary storage system in S102 of FIG. 8;

FIG. 11 shows a configuration example of Extent Management Table;

FIG. 12 illustrates how the presence of duplicate files is determined inS102 of FIG. 8;

FIG. 13 shows an example of address control processing flow executed inS102 of FIG. 8;

FIG. 14A shows that a selected hash value and a matching hash value arepresent in one Extent Management Table;

FIG. 14B shows an example of update results of the Extent ManagementTable in the case shown in FIG. 14A;

FIG. 15A shows that a selected hash value and a matching hash value arepresent in different Extent Management Tables;

FIG. 15B shows an example of update results of the Extent ManagementTable where the selected hash value is present in the case shown in FIG.15A;

FIG. 16A shows migration between LDEV in S103 of FIG. 8;

FIG. 16B shows an example of the LDEV Management Table before themigration;

FIG. 16C shows an example of the LDEV Management Table during migration;

FIG. 16D shows an example of an Address Map Management Table before themigration and during the migration;

FIG. 17 shows an access path after the migration;

FIG. 18A shows an example of a GUI before the migration that isdisplayed by a Program of UI Control;

FIG. 18B shows an example of a GUI after the migration;

FIG. 19A shows an elimination determination criterion in the firstembodiment and the results of address change according to thiscriterion;

FIG. 19B shows an elimination determination criterion in the secondembodiment and the results of address change according to thiscriterion;

FIG. 20 shows a configuration example of an Address Map Management Tablein the second embodiment;

FIG. 21 shows an example of address control processing flow in thesecond embodiment;

FIG. 22A shows an example of LDEV Management Table after the migrationin the first embodiment; and

FIG. 22B shows an example of an Address Map Management Table after themigration.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In one embodiment of the present invention, a computer and a firststorage system having one or more first logical storage devices where aplurality of files are stored are provided. The computer can comprise anintrinsic value calculation unit that calculates a plurality of contentsintrinsic values that are values intrinsic to contents of a plurality offiles, an intrinsic value transmission unit that transmits a pluralityof contents intrinsic values corresponding respectively to the pluralityof files to the first storage system. The first storage system comprisesa duplication determination unit that determines whether two or moreidentical contents intrinsic values are contained in the plurality ofcontents intrinsic values, and a change control unit that changes anaccess destination of a first file corresponding to a first contentsintrinsic value from among these two or more contents intrinsic valuesto a position having stored therein a second file corresponding to asecond contents intrinsic value from among these two or more contentsintrinsic values, when there are the two or more identical contentsintrinsic values.

In one embodiment, the intrinsic value calculation unit can calculate aplurality of contents intrinsic values when the plurality of files aretaken as archive objects. More specifically, for example, the intrinsicvalue calculation unit can calculate the contents intrinsic values byusing a hash function with respect to a file contents based oninformation (for example, i-node information) indicating a storageposition of a file that is managed by a file system used by a NAS nodethat transits an access request to the first storage system when theplurality of files are taken as archive objects.

In one embodiment, the intrinsic value calculation unit can prohibit thefirst storage system from updating one or more first logical storagedevices when a plurality of files are taken as archive objects. Aplurality of files taken as archive objects can be designated in avariety of units such as file units, directory units, file system units,and first logical storage device units. Further, the “archive object” asreferred to herein is a can man an object that cannot be updated. Theupdate of each of one or more first logical storage devices that store aplurality of files that are unupdatable is prohibited.

In one embodiment, there are a plurality of storage period limits thatare respectively associated with a plurality of contents intrinsicvalues. The change control unit changes an access destination of thefirst file corresponding to the first storage period limit to a positionhaving stored therein the second file corresponding to a second storageperiod limit that is longer than the first storage period unit, fromamong two or more storage period limits respectively corresponding totwo or more identical contents intrinsic values.

In one embodiment, a second storage system comprising one or more secondlogical storage devices is connected to the first storage system. Thefirst storage system can further comprise one or more virtual logicalstorage devices respectively associated with one or more second logicalstorage devices, and a migration execution unit that writes a body ofeach file stored in the one or more first logical storage devices to theone or more second logical storage devices via one or more virtuallogical storage devices of migration destination. The migrationexecution unit does not write a body of the first file into any of oneor more second logical storage devices and writes a body of the secondfile into any of one or more second logical storage devices from amongtwo or more files respectively corresponding to two or more identicalcontents intrinsic values. The change control unit can change an accessdestination of the first file to a position where a body of the secondfile has been written.

In one possible embodiment, before the migration is started, none of theone or more first logical storage devices that store the plurality offiles can be updated. After the migration is completed, each of the oneor more virtual logical storage devices can be updated, but none of theplurality of files that have become the object of the migration can beupdated.

In one embodiment, the change control unit can further control thechange of access destination based on a device characteristic of one ormore second logical storage devices.

In one embodiment, a migration destination of a first file correspondingto the longest storage period limit and a second file that is anotherfile, from among two or more storage period limits respectivelycorresponding to two or more identical contents intrinsic values, istaken as a first virtual logical storage device corresponding to a firstsecond logical storage device having a device characteristic of a firsttype (for example, a characteristic of a low speed). A migrationdestination of a third file with a storage period limit longer than thestorage period limit of the second file is taken as a second virtuallogical storage device corresponding to a second logical storage devicehaving a device characteristic of a second type (for example, acharacteristic of a high speed) that is superior to the devicecharacteristic of the first type. In this case, the change control unitcan change an access destination of the second file to a position havingstored therein a body of the third file. Further, the migrationexecution unit can write a body of the first file into the first secondlogical storage device via the first virtual logical storage device,does not write a body of the second file to the first second logicalstorage device, and can write a body of the third file into the secondlogical storage device via the second virtual logical storage device.

In one embodiment, for example, because a failure has occurred in thefirst second logical storage device, the change control unit can changean access destination of the first file to a position where a positionof the third file is stored, when reading of a body of the first filefrom the first second logical storage device is impossible. Further, forexample, because a failure has occurred in the second logical storagedevice, the change control unit can change an access destination of thethird file to a position where a body of the first file is stored whenreading of a body of the third file from the second logical storagedevice is impossible.

In one embodiment, the computer can further comprise a storage area anda completeness check unit. The first storage system can further comprisea storage region that stores a plurality of contents intrinsic valuesreceived from the computer. The intrinsic value calculation unit canstore a plurality of contents intrinsic values in the storage area ofthe computer. The completeness check unit can compare a contentsintrinsic value from among a plurality of contents intrinsic values thatare stored in the storage area of the computer, this contents intrinsicvalue corresponding to the file selected from a plurality of files, witha contents intrinsic value corresponding to the selected file that hasbeen stored in the storage area of the first storage system.

In one embodiment, the first storage system can further comprise a savedcapacity notification unit. The saved capacity notification unit cancalculate a storage capacity saved by changing the access destination ofthe first file and send information indicating this storage capacity tothe computer.

In one embodiment, the change control unit can change the accessdestination by updating a change management table having a plurality ofrecords respectively corresponding to a plurality of files. A fieldhaving recorded therein a record ID, position information of the file,and a record ID of a reference destination is present in one recordcorresponding to one file. The change control unit can update the recordID of the reference destination to a record ID on the second recordcorresponding to the second file in a first record corresponding to thefirst file. The record can use a flag indicating whether of not tochange. For example, the change control unit can set to On the flagcorresponding to the first file for which the address destination willbe changed.

In one embodiment, a storage period limit of a file and an accessattribution of a file may be further recorded in one record of thechange management table. The change control unit can update a referencedestination record ID on the second record of the second filecorresponding to a second storage period limit that is longer than afirst storage period limit, from among two or more storage period limitsrespectively corresponding to the two or more identical contentsintrinsic values, to an ID on the first record of the first filecorresponding to the first storage period limit and set an accessattribution on the first and second records to Read Only. In this case,even if the first storage system receives a write access that designateda position shown by a position information on the first and secondrecords, writing to this position is not executed.

Any two or more of the above-described multiple embodiments can becombined together. The above-described computer may be a managementcomputer for managing the first storage system. Alternatively, it may bea NAS node for transmitting an access request to the first storagesystem. Further, various components of the above-described computer maybe also provided in the first storage system.

Each of the above-described units (for example, the intrinsic valuecalculation unit, duplication determination unit, change control unit,etc.) can be implemented of hardware (for example, a circuit), acomputer program, or a combination thereof (for example, one or aplurality of CPU that read and execute a computer program). Eachcomputer program can be read from storage resources (for example, amemory) provided in the computer. The programs can be installed via astorage medium such as a CD-ROM or a DVD (Digital Versatile Disk) ordownloaded via a communication network such as Internet or LAN into thestorage resources.

Several embodiments of the present invention will be described below ingreater detail. In the explanation below, the first storage system willbe referred to as “primary storage system”, and the second storagesystem will be referred to as “secondary storage system”. The elements(for example, memory) located in the primary storage system will bereferred to as “internal elements”, and the elements in the secondarystorage system located outside the primary storage system will bereferred to as “external elements”. Furthermore, identical elements willbe explained by using identical parent numbers, and when identicalelements are distinguished, the explanation uses parent numbers andchild numbers.

First Embodiment

FIG. 1 is a block diagram illustrating a configuration example of thecomputer system of the first embodiment of the present invention.

A NAS node 10 and a primary storage system 600 are connected to a firstcommunication network (for example, a SAN (Storage Area Network)) 105.The primary storage system 600 and a secondary storage system 40 areconnected to a second communication network 104 (for example, a SAN).The NAS node (for example, a file server) 10, a client 301, the primarystorage system 600, and a management terminal 106 are connected to athird communication network (for example, a LAN (Local Area Network))107. At least two from among a plurality of communication networks 105,104, and 107 may be one communication network. The communicationnetworks 105, 104, and 107 can employ various communication networks. Atleast one from among a plurality of communication networks 105, 104, and107 may be a special line.

At least one from among the client 301, the NAS node 10, and themanagement terminal 106 is, for example, a computer device comprising aCPU (Central Processing Unit) and information processing resources suchas a memory. For example, the computer device can be configured as apersonal computer, a workstation, and a mainframe.

The client 301 can transmit a file access request (file read request orfile write request) to the NAS node 10 based on a general protocol (forexample, NFS (Network File System) or CIFS (Common Internet FileSystem)) with respect to the NAS node 10.

The NAS node 10 receives the file access request from the client 301,creates a block access request for writing the file body (for example, aplurality of data blocks) corresponding to the received file accessrequest into a logical storage device (sometimes referred to hereinbelowas “LDEV”, which is the abbreviation of Logical Device) located insidethe primary storage system 600, or reading the file body from the LDEV,and transmits the created block access request. A file management deviceof a different kind can be also employed instead of the NAS node 10.

The primary storage system 600 can be, for example, a RAID (RedundantArray of Independent (or Inexpensive) Disks) comprising a multiplicityof disks 400 arranged as an array. Such configuration is, however, notlimiting, and the primary storage system 600 can be also configured as astorage virtualization device of another kind, for example, as a switch(more specifically, a fiber channel switch of an intelligent type withincreased functionality) that constitutes the communication network.Because, the primary storage system 600, as will be described below,provides storage resources of the secondary storage system 40 to the NASnode 10, as its own LDEV, the primary system may have no local storagedevices that are directly supported by itself.

The primary storage system 600 can be generally classified into acontroller unit 20 and a disk unit 30. The controller unit 20 comprises,for example, a channel adapter (referred to hereinbelow as CHA) 21, adisk adapter (referred to hereinbelow as DKA) 22, a SVP (ServiceProcessor) 23, a cache memory 24, a shared memory 25, and a connectionunit 26.

The CHA 21 performs data communication with an external device (forexample, the NAS node 10 or secondary storage system 40) via acommunication port 207. For example, the CHA 21 is configured as amicrocomputer system comprising a CPU, a memory, and the like. A networkaddress (for example, WWN (World Wide Name)) for identifying the CHA 21is allocated to the CHA 21. A CHA 21A that is connected to the NAS node10 and a CHA 21B that is connected to the secondary storage system 40are contained in the CHA 21. The CHA 21A and CHA 21B may be integrated.

The DKA 22 has a communication port 220 for connection to a disk(referred to hereinbelow as “internal disk”) 400 provided in the diskunit 30 and can communicate with the internal disk 400 via thecommunication port 220. The DKA 22 is configured as a microcomputersystem comprising a CPU, a memory, and the like. The DKA 22 can writethe data that were written from the CHA 21A to the cache memory 24 intothe internal disk 400 or write the data that were read from the internaldisk 400 to the cache memory 24. Furthermore, the DKA 22 can convert alogical address into a physical address when performing datainput/output with the internal disk 400.

The cache memory 24 is, for example, a volatile or nonvolatile memoryand can temporarily store the data that were received from the NAS node10 and transferred into an internal LDEV 31 or an external LDEV 42, orthe data that were read from the internal LDEV 31 or the external LDEV42.

The shared memory 25 is, for example, a nonvolatile memory that storesinformation (for example, control information) relating to the controlof the primary storage system 600. Examples of control informationinclude the below described Contents Identifier Management Table,Address Map Management Table, and Extent Management Table.

The connection unit 26 serves to connect the CHA 21, DKA 22, cachememory 24, and shared memory 25 to each other. The connection unit 26can be configured, for example, as a high-speed bus such as anultrahigh-speed crossbar switch that performs data transmission byhigh-speed switching operation.

The disk unit 30 comprises a plurality of internal disks 400 arranged asan array. Disk-type storage devices such as hard disks, flexible disks,and optical disks can be used as the internal disks 400. A variety ofother storage devices, for example, magnetic tapes and semiconductormemory (for example, flash memory) can be used instead of the internaldisks 400. A logical storage device (internal LDEV) 31 is provided onthe storage area of the internal disk 400. The internal LDEV 31 is areal LDEV that was set by using storage resources of the physicalinternal disk 400, whereas the LDEV 132 is a virtual LDEV, rather thanthe LDEV that was set by using the internal disk 400. The internal LDEV31 will be referred to hereinbelow as a real internal LDEV 31, and theLDEV 132 will be referred to as a virtual internal LDEV 132. When anaccess is generated to the real internal LDEV 31, the access isperformed to the internal disk 400, but when access is generated to thevirtual internal LDEV 132, the access is performed to the external LDEV42. The technology of this type is sometimes called the externalconnection technology, and, for example, each LUN (Logical Unit Number)of the virtual internal LDEV 132 and the external LDEV 42 may beassociated at a 1:1 ratio, or a technology disclosed in Japanese PatentApplication Laid-open No. 2005-107645 (U.S. patent application Ser. No.10/769,805, U.S. patent application Ser. No. 11/471,556) may beemployed.

The SVP 23 is an information processing terminal (for example, anotebook personal computer) for performing maintenance or management ofthe primary storage system 600. The SVP 23 is connected, for example,via the internal line LAN 410 to a processor (for example, CPU) locatedin the CHA 21 or to a processor located in the DKA 22. The SVP 23monitors the occurrence of malfunction inside the primary storage system600 and displays it on a display screen, or instructs to performblocking processing of the internal disk 400. The SVP 23 can bemonitored from a remote management terminal 106.

The secondary storage system 40 may have the configuration of theprimary storage system 600, or may have a configuration simpler thanthat of the primary storage system 600. For example, the secondarystorage system 40 comprises a CHA 217 having a communication port 41 andone or a plurality of disks (referred to hereinbelow as “externaldisks”) 500. The external LDEV 42 is provided on the storage area of theexternal disk 500. The external LDEV 42 is handled as the internal LDEV132 of the primary storage system 600.

A configuration example of the computer system of the present embodimentis described above. Such a configuration is, however, but one example,and other configurations may be also employed. For example, rather thanusing the shared memory 25 and the cache memory 24 separately, onememory may be provided with a shared memory area and a cache memoryarea. Further, for example, the controller unit 20 may be a circuitboard comprising a CPU, a memory, and a communication port. In thiscase, the CPU can execute the processing performed by a plurality of CHAor DKA. Further, a CHA having a function of the NAS node 10, in otherwords, a CHA that can function as a NAS (for the sake of convenience, itwill be referred to hereinbelow as Embedded NAS, or “E-NAS”, in anabbreviated form) may be installed in place of the CHA 21A in theprimary storage system 600. In this case, the E-NAS may receive a filerequest from the client 301 and conduct processing by creating a blockaccess request from the file access request.

The present embodiment will be described below in greater detail.

FIG. 2A shows an example of a computer program to be executed by the CPUlocated in the controller unit 20 of the primary storage system 600.When a computer program becomes a subject, as described hereinbelow, itactually means the performance of the processing by the CPU executingthe computer program.

Examples of the programs include a Program 701 of Migration Executionthat executes migration between LDEV, a Program 705 of DeterminationControl that determines whether the files duplicate and updates theExtent Management Table, a Program 707 of Access Control that controlsthe processing of the block access request from the NAS node 10, and aProgram 709 of Table Provision that provides an LDEV Management Table.These computer programs 701, 705, 707, and 709 may be present in one ofthe storage resources located in the SVP 23, storage resources locatedin the CHA 21A, storage resources located in the CHA 21B, storageresources located in the DKA 22, internal disks 400, shared memory 25,and cache memory 24, or in a plurality thereof. These computer programs701, 705, 707, and 709 may be executed in one or a plurality of the CPUlocated in the SVP 23, CPU located in the CHA 21A, CPU located in theCHA 21B, and CPU located in the DKA 22.

FIG. 2B is a configuration example of the Address Map Management Table.

The Address Map Management Table 801 is a table for managing theassociation of the virtual internal LDEV 132 and external LDEV 42 and isstored in the storage resources (for example, the shared memory 25)located in the primary storage system 600. For example, an identifier(LDEV number (VDEV number)) 8011 of the virtual internal LDEV 132, a WWN(World Wide Name) (or information of other type, such as a port number)8012 corresponding to the external LDEV 42 associated therewith, and aLUN (Logical Unit Number) 8013 corresponding to the external LDEV 42 arerecorded in the table 801.

FIG. 2C shows a configuration example of the LDEV Management Table.

The LDEV Management Table 803 is stored, for example, in the storageresources (for example, the shared memory 25) located in the primarystorage system 600. The LDEV Management Table 803 is a table forrecording information relating to the internal LDEV 31, 132. Forexample, a port number 8031, a LUN 8032, a LDEV number 8033, an accessattribution 8034, a LDEV type 8035, and a usage state 8036 are recordedwith respect to one internal LDEV (called “object internal LDEV” in theexplanation of FIG. 2C hereinbelow) in one record of the table 803. Theport number 8031 is an identifier (for example, a WWN) of the portcorresponding to the object internal LDEV. The LUN 8032 is a LUNcorresponding to the object internal LDEV. The LDEV number 8033 is thenumber of the object internal LDEV. If the port number 8031 and the LUN8032 are indicated by a block access command, then access to theinternal LDEV associated therewith is executed. The access attribution8034 is the information for limiting the type of access to the objectinternal LDEV. Examples of such information include Read/Write (both thereading and the writing are allowed) and Read Only (only reading isallowed, and writing is prohibited). The Program 707 of Access Controldoes not update the internal LDEV even if a block write command isreceived for the internal LDEV corresponding to the “Read Only” accessattribution 8034. The LDEV type 8035 is information indicating the typeof the object internal LDEV. For example, it can be a real internal LDEV(“R”) or a virtual internal LDEV (“V”). The usage state 8036 isinformation indicating the usage state of the object internal LDEV. Forexample, it is “In Use” or “Not Used”.

FIG. 3 shows a configuration example of the management terminal 106.

The Utility Program 715 that is executed by the CPU 711 of themanagement terminal 106 is stored in storage resources (for example, atleast one from among a memory and a disk device) 713 of the managementterminal 106. In the present embodiment, the Utility Program 715 isexecuted by the management terminal 106, but instead it may be executedby another computer such as the NAS node 10.

The Utility Program 715 includes, for example, a Program 717 ofInformation Collection, a Program 719 of Hash Creation, and a Program721 of User Interface (UI) Control.

As shown in FIG. 4, the Program 717 of Information Collection collectsinformation of the predetermined types from the NAS node 10 and theprimary storage system 600. An example of the collected information isshown in FIG. 5 and FIG. 6. The information shown by way of an examplein FIG. 5 is Tables 811 and 813 of directory file information (refereedto hereinbelow as “Directory File Management Tables”) that are managedby the File System Program 721 of the NAS node 10. The File SystemProgram 721 is a computer program using a file system of one or aplurality of internal LDEV. A file can be acquired by referring to thecontents described in the address of the Table 813 that is indicated bythe i node information of the Table 811. The information shown by way ofan example in FIG. 6 is a Table 831 in which information (informationrelating to a logical volume storing a file or a directory) managed by avolume manager 723 of the NAS node 10 is recorded and an LDEV ManagementTable Portion 833 that is a portion of an LDEV Management Table 803 (seeFIG. 2C) managed by the primary storage system 600. A directory pointname 8313, a device file name 8312, and a disk group name 8311 arerecorded in the records of the Table 831. Further, a port number 8331, aLUN 8332, and a LDEV number 8333 (for example, values identical to thoseof 8031, 8032, and 8033 of FIG. 2C) are recorded for each internal LDEV31, 132 in the Table Portion 833. A combination of the directory pointname 8313, device file name 8312, and disk group name 8311 of the filesystem corresponds to one internal LDEV. Which combination correspondsto which internal LDEV can be specified, for example, by the numericalvalue in the device file name 8312 (for example, c0 means the primarystorage system 600, t1 means the port number “1”, and d1 means the LUN“1”). More specifically, for example, according to the example shown inFIG. 4, FIG. 5, and FIG. 6, it is clear that an internal LDEVcorresponding to a file system having “/usr” as a route directory is aninternal LDEV corresponding to a the port number “1”, LUN “1”, and LDEVnumber “1” (00:01). The above-described logical volume is a logicalstorage device recognized by the volume manager 723 and corresponds tothe internal LDEV 31, 132 in the primary storage system 600.

The Program 719 of Hash Creation creates a Contents IdentifierManagement Table 835 shown by way of an example in FIG. 7 for oneinternal LDEV. One record of the Table 835 corresponds to one file. Inone record, there are recorded a hash value (in other words, anidentifier of the file contents) 8351 of the file corresponding to therecord, an address (for example, a block number) 8352 indicating aposition (position within the internal LDEV) where block dataconstituting the file have been saved, a file name 8353 of the file, afile address (for example, an address (for example, a path name to thedirectory storing the file) of the file managed by an i node)) 8354 ofthe file, and a storage period limit 8355 of the file. The Program 719of Hash Creation calculates a hash value of the file from i nodeinformation (information recorded in the Directory File ManagementTables 811 and 813) collected from the NAS node 10 by specifying thefile contents and hash converting the file contents (by using a hashfunction). This hash value is sometimes referred to hereinbelow as“contents identifier”. The storage period limit 8355 is, for example,information inputted by the user via a GUI shown by way of an example inthe below-described FIG. 18A. The storage period limit 8355 may be alsoobtained by setting a value in advance in a file and copying this presetvalue, instead of inputting from the user. Further, informationindicating the storage period may be also employed instead of thestorage period limit 8355. Both the storage period limit and the storageperiod represent information indicating for how long a file has to bestored.

The Program 721 of UI Control can display a GUI (Graphical UserInterface) shown by way of an example in FIG. 18A based on theinformation shown in FIG. 5 and FIG. 6 at a display device (for example,a display device of the management terminal 160). For example, theProgram 721 of UI Control can display information relating to aplurality of LDEV in the GUI, receive the selection desired by the userfrom among a plurality of LDEV, and display information relating to atleast one directory and/or at least one file stored in the LDEV selectedby the user. Further, the program 721 of UI control receives the inputof information indicating the storage period limit for at least one ofeach file, and when the information indicating the storage period limitfor a certain file is inputted, the program records the inputtedinformation as the storage period limit 8355 in the Contents IdentifierManagement Table 835 corresponding to the LDEV that stores this file.

The processing flow performed by the computer system of the presentembodiment was described above. In the explanation below, it will beassumed that the association has been established between the Table 831and the Table Portion 833 shown by way of an example in FIG. 6 and thatinformation that is the object of subsequent collection is theinformation shown by way of an example in FIG. 5. Further, quadrangleswithin the LDEV and quadrangles within the FSP (File System Program) inFIG. 9 and FIG. 10 indicate files. Files with the same colorationpattern are files with identical contents. Therefore, hash values of thefile contents are also assumed to be identical.

<S101 of FIG. 8: Archive Instruction>

The Program 717 of Information Collection of the Utility Program 715issues an information inquiry to the NAS node 10 or primary storagesystem 600. In response to the inquiry received by the NAS node 10, apredetermined computer program (for example, an agent program) transmitsthe Tables 811, 813 shown in FIG. 5 or the Table 831 shown in FIG. 6 tothe Utility Program 715. In response to the information inquiry receivedby the primary storage system 600, the Program 709 of Table Provisiontransmits the LDEV Management Table Portion 833 to the Utility Program715. The Program 717 of Information Collection associates the LDEVManagement Table Portion 833 with the Table 831 as shown in FIG. 6. Asfor the correspondence relationship between the file, directory, andinternal LDEV 31, 132, which file or which directory is stored in whichinternal LDEV is clear from the information shown in FIG. 5 and FIG. 6.

In response to completion of information selection, the Program 721 ofUI Control displays the GUI shown in FIG. 18A, and the user receives anarchive indication via the GUI in units of at least one type selectedfrom among the internal LDEV units, directory units, and file units. Ifan archive indication is received that indicates at least one from theinternal LDEV, directory, and file desired by the user, the Program 721of UI Control sets the access attribution 8034 in the LDEV ManagementTable 803 relating to the indicated internal LDEV or the internal LDEVthat stores the indicated directory or file (sometimes, these internalLDEV will be together referred to hereinbelow as “internal LDEV of thearchive indication object”) to “Read Only”, as shown by way of anexample in FIG. 9. In the example shown in FIG. 9, an internal LDEV #1and an internal LDEV #2 are internal LDEV of the archive indicationobject, and “Read Only” of the access attribution 8034 is assumed to beset for each internal LDEV. The description “internal LDEV #1” means aninternal LDEV for which the LDEV number 8033 is “1” (00:11).

Instead of setting the access attribution 8034 “Read Only”, according toanother method, it is possible to avoid writing into the internal LDEVof the archive indication object. For example, when the primary storagesystem 600 receives the indication of the internal LDEV of the archiveindication object and then receives a block access command thatindicates the internal LDEV, the primary storage system may inhibitwriting by returning the predetermined response such as “WriteImpossible” or “Busy”.

Further, for example, the Program 721 of UI Control can also receive thestorage period limit via the GUI shown in FIG. 18A for the file desiredby the user. When the storage period limit has been received, theProgram 721 of UI Control stores the corresponding relationship betweenthe file name 8353 and the storage period limit 8355 in the storageresources 713, and when the Contents Identifier Management Table 835 iscreated, this storage period limit 8355 can be recorded in the Table835.

Further, for example, the Program 721 of UI Control may receive thedesignation of the internal LDEV that will be a migration source via theGUI shown in FIG. 18A. Instead, the Program 721 of UI Control may alsotake the internal LDEV designated as the archive indication object (oran internal LDEV that stored a file or directory designated as thearchive indication object) as the internal LDEV of a migration source,without special indication from the user.

For example, if the archive object is designated in the internal LDEVunits and the association between the Table 831 and Table Portion 833shown in FIG. 6 is established, the Table 811 and Table Portion 813shown in FIG. 5 may be acquired from the NAS node 10 in the next stepS102, without performing information collection in this step S101.

<S102 of FIG. 8: File Duplication Determination/Address Change Control>

For example, in response to the completion of setting the accessattribution 8034 “Read Only” in S101, the Program 719 of Hash Creationcreates the Contents Identifier Management Table 835 for each internalLDEV that is the archive indication object. This procedure will beexplained below with reference to one internal LDEV. For example, theProgram 719 of Hash Creation refers to the Tables 311 and 313 shown inFIG. 5, calculates the hash values of the file contents for each filestored in the internal LDEV, specifies the real storage position of thefile (for example, a block number for identifying a block within theinternal LDEV), and records the calculated hash values 8351 togetherwith the specified address (physical storage position) 8352, file name8353, and file address 8354 in the Contents Identifier Management Table835. Further, the Program 719 of Hash Creation records the storageperiod (storage period limit inputted by the user via the GUI in S101)8355 that has been stored in the storage resources 713 in the ContentsIdentifier Management Table 835.

As shown in FIG. 10, the Program 719 of Hash Creation transmits theContents Identifier Management Table 835 for each internal LDEV that isthe archive indication object to the primary storage system 600, and theprimary storage system 600 receives this table. The Program 705 ofDetermination Control stores the received Contents Identifier ManagementTable 835 in the storage resources (for example, the shared memory 25)located in the primary storage system 600.

The Program 705 of Determination Control creates an Extent ManagementTable for each internal LDEV that is the archive indication object basedon the Contents Identifier Management Table 835 for each internal LDEVthat is the archive indication object. FIG. 11 shows an example of theExtent Management Table. One record of the Extent Management Table 861(referred to hereinbelow as “extent record”) corresponds to one recordof the Contents Identifier Management Table 835 (referred to hereinbelowas “hash record”) and, therefore, corresponds to one file. One extentrecord has recorded therein an ID 8611, an address 8612, an accessattribution 8613, a storage period limit 8614, a change flag 8615, anextent ID 8616, and a VDEV number 8617. The ID 8611 is, for example, asequence number of the corresponding hash record. The address 8612 is acopy of the address 8352 recorded in the corresponding hash record. Theaccess attribution 8613 is information (for example, Write/Read, ReadOnly) indicating the access attribution for the corresponding file.Immediately after the Extent Management Table 861 has been created, acopy of the access attribution 8034 for the internal LDEV correspondingto the Table 861 is recorded in all the extent records. The storageperiod limit 8614 is, for example, a copy of the storage period limit8355 that has been recorded in the corresponding hash record. The changeflag 8615 is a flag indicating whether (On) or not (Off) the address ischanged. The extent ID 8616 is a value that is set when the change flagis “On” and indicates the ID 8611 that has to be referred to. The VDEVnumber 8617 is a value that is set when the change flag 8615 is “On” andindicates the LDEV number (VDEV number) 8011 (LDEV number (VDEV) number8011 that has been recorded in the Address Map Management Table 801)that has to be referred to. Immediately after the Extent ManagementTable 861 has been created, the change flag 8615 becomes “Off” in allthe extent records, and the storage areas of the extent ID 8616 and theVDEV number 8617 become blank or ineffective values are set therein.

The Program 705 of Determination Control determines whether theduplicate files are present and performs the address change control, asshown in FIG. 12. More specifically, the address control processingshown by way of an example in FIG. 13 is executed.

Thus, the Program 705 of Determination Control refers to the ContentsIdentifier Management Table 835 selected from all the recorded ContentsIdentifier Management Tables 835 (S1) and retrieves from the ContentsIdentifier Management Table 835 a hash value (referred to hereinbelow as“matching hash value”) 8351 that matches the hash value (referred tohereinbelow as “selected hash value”) 8351 selected from the Table 835(S2). If no matching hash value 8351 is found in the Table 835 (S3: NO,S4: YES) and if another Contents Identifier Management Table 835 thathas not yet been referred to is present (S5: NO), then the Program 705of Determination Control refers to the other Contents IdentifierManagement Table 835 (S6) and retrieves the matching hash value 8351from this Table 835.

In the case where the matching hash value 8351 has been found (S3: YES),the Program 705 of Determination Control refers to and compares onestorage period limit 8355 (storage period limit 8355 corresponding tothe selected hash value 8351) and another storage period limit 8355(storage period limit 8355 corresponding to the matching hash value8351) (S7). If the period indicated by one storage period limit 8355 islonger, the process flow advances to step S11. If the period indicatedby one storage period limit 8355 is shorter, the Program 705 ofDetermination Control sets one change flag 8615 (change flag 8615corresponding to the selected hash value 8351) to “On” (S9). Further, ifthe matching has value 8351 was found from the other Contents IdentifierManagement Table 835, the Program 705 of Determination Control recordsthe LDEV number of the internal LDEV corresponding to this Table 835 asone VDEV number 8617 (change flag 8615 corresponding to the selectedhash value 8351) (S10).

In step S11, the Program 705 of Determination Control determines whetheror not all the hash codes of the Table 835 that is the present referenceobject have been referred to, and if all the hash codes have not beenreferred to (S11: NO), the processing flow returns to step S2, whereasif all the hash codes have been referred to (S11: YES), the processingflow advances to S12. In step S12, the Program 705 of DeterminationControl determines the presence of the Contents Identifier ManagementTable 835 that has not been referred to, and if the Table 835 that hasnot been referred to is present (S12: YES), this table is referred to(S13), and if such table is absent (S12: NO), the processing ends.

In the explanation referring to FIG. 13, in the case where the matchinghash value 8351 is found from the Contents Identifier Management Table835 where the selected hash value 8351 is present, as shown by way of anexample in FIG. 14A, the Extent Management Table 861 corresponding tothis Table 835 is updated, for example, as shown in FIG. 14B. Thus, ifan ID 8611 corresponding to the selected hash value 8351 is taken as “1”and an ID 8611 corresponding to the matching hash value 8351 is taken as“0”, then the storage period limit 8614 “2010.01.01” corresponding tothe ID 8611 “1” will be shorter than the storage period limit 8614“2020.01.01” corresponding to the ID 8611 “0”. Therefore, the changeflag 8615 corresponding to the ID 8611 “1” will be made “On” and theextent ID 8616 corresponding thereto will be made “0”. As a consequence,in the case where a file access request designating a file correspondingto ID “1” is transmitted from the client 301, a file corresponding to ID“0” is supplied to the client 301.

On the other hand, in the explanation referring to FIG. 13, as shown byway of an example in FIG. 15A, when a matching hash value 8351 is foundfrom the second Contents Identifier Management Table 835 that isdifferent from the first Contents Identifier Management Table 835 wherethe selected hash value 8351 is present, the first Extent ManagementTable 861 corresponding to the first Contents Identifier ManagementTable 835 and the second Extent Management Table 861 corresponding tothe second Contents Identifier Management Table 835 are updated, forexample as shown in FIG. 15B. Thus, if an ID 8611 corresponding to theselected hash value 8351 is taken as “10” (located in the second ExtentManagement Table 861) and an ID 8611 corresponding to the matching hashvalue 8351 is taken as “0” (located in the first Extent Management Table861), then the storage period limit 8614 “2010.01.01” corresponding tothe ID 8611 “10” will be shorter than the storage period limit 8614“2020.01.01” corresponding to the ID 8611 “0”. Therefore, the changeflag 8615 corresponding to the ID 8611 “1” will be made “On” and theextent ID 8616 corresponding thereto will be made “0”. Furthermore, theVDEV number 8617 corresponding to the ID “10” will be taken as the LDEVnumber “01” of the internal LDEV corresponding to the first ExtentManagement Table 861.

The step S102 shown in FIG. 8 is explained above. In this step S102, theUtility Program 715 or Program 705 of Determination Control may deletethe body of at least one file other than the one file from among aplurality of duplicate files, based on the created Contents IdentifierManagement Table 835, before the migration relating to the secondarysystem 40 is executed in the below-described step S103 shown in FIG. 8.Further, the file body may be replaced, rather than deleted, with a link(for example, a symbolic link or a shortcut) indicating the file body.In this case, where the access attribution 8613 has been set in advanceas “Read Only”, in order to perform deletion or replacement, the UtilityProgram 715 or Program 705 of Determination Control may temporarilycancel the setting of the access attribution 8613, complete the deletionor link replacement processing, and then again set the accessattribution 8613 to “Read Only”. When the deletion or link replacementhas been performed in this step S102, the migration of S103 of FIG. 8may be performed simply as the migration between LDEV (between logicalvolumes). In other cases, as described below, the migration may beperformed based on the change flag 8615 of the Extent Management Table861 of the migration source.

<S103 of FIG. 8: Migration Between LDEV>

For example, in response to the processing flow explained with referenceto FIG. 13, the Program 701 of Migration Execution located within theprimary storage system 600 can determine the migration destination ofdata located within the real internal LDEV #1, #2 that are the archiveindication objects as virtual internal LDEV #3, #4, as shown in FIG.16A.

In the present embodiment, a file is stored in the real internal LDEVand the file read or write is executed with respect to the real internalLDEV before the archive indication. As a result, the internal LDEV thatis the archive indication object is a real internal LDEV, and theinternal LDEV that is the migration source is, therefore, also the realinternal LDEV. By contrast, the migration destination is a virtualinternal LDEV, as shown by way of an example in FIG. 16A. Morespecifically, for example, before the migration, as shown in FIG. 16B,the LDEV types 8035 corresponding to the LDEV number 8033 “3” and “4”are all “V” in the LDEV Management Table 803 and the usage state 8036 is“Not Used”. As a result, as shown in FIG. 16C, the LDEV number (VDEVnumber) 8011 is taken as “03” and “04” in the Address Map ManagementTable 801. In this case, the migration execution program 701 refers tothe LDEV Management Table 803 and determines the migration destinationof data that have been stored in the real internal LDEV #1, #2 as thevirtual internal LDEV #3, #4, respectively. Furthermore, the migrationexecution program 701 can update the usage states 8036 corresponding tothe LDEV numbers 8033 “3” and “4” to “In Use”. The migration destinationmay be determined automatically as described hereinabove, or may bedetermined manually via a GUI displayed by the Program 721 of UIControl.

The Program 701 of Migration Execution initiates the migration of datalocated in the real internal LDEV #1, #2 to the virtual internal LDEV#3, #4. If the NAS node 10 receives from the client 301 the file readrequest that designates the file that has been stored in the realinternal LDEV #1 in the course of the migration, the NAS node 10transmits the block read request designating the internal LDEV #1 to theprimary storage system 600. The LDEV Management Table 803 is, forexample, such as shown by way of an example in FIG. 16C, and the Program707 of Access Control reads data from the real internal LDEV #1 andtransmits them to the NAS node 10 according to this block read request.In other words, the client 301 can read the file that is the archiveobject via the NAS node 10 even during the migration.

When the Program 701 of Migration Execution performs the migration ofdata located in a position within the real internal LDEV #1 that isspecified, for example, from a certain address 8612 to the virtualinternal LDEV #3, the program refers to the change flag 8615corresponding to this address 8612, and when the change flag 8615 is“Off”, the data are migrated to the virtual internal LDEV #3, whereaswhen the change flag 8615 is “On”, the data are not migrated to thevirtual internal LDEV #3 (for example, these data may be deleted). Inother words, the data of at least one file other than the one file ofthe duplicate files are not migrated to the virtual internal LDEV of themigration destination. In other words, the amount of data that iswritten into the virtual internal LDEV of the migration destination canbe decreased by comparison with the amount of data that has been storedin the real internal LDEV of the migration source. For example, for thedata that were migrated to the virtual internal LDEV #3, an externalLDEV corresponding to the virtual internal LDEV #3 is specified from theAddress Map Management Table 801 by the migration execution program 701,and the block right command that designates the WWN 8012 or LUN 8013 ofthe specified external LDEV is transmitted to the primary storage system40.

Once the migration has been completed, the Program 701 of MigrationExecution exchanges the LDEV numbers of the migration source andmigration destination, as shown in FIG. 17. More specifically, forexample, the Program 701 of Migration Execution exchanges the portnumber 8031, LUN 8032, and LDEV number 8033 of the migration source andthe port number 8031, LUN 8032, and LDEV number 8033 of the migrationdestination in the LDEV Management Table 803, as shown in FIG. 22A(furthermore, the usage state 8036 of the internal LDEV #3, #4 may bechanged to “Not Used”, as shown in FIG. 22A). Further, the Program 701of Migration Execution overwrites the LDEV number 8033 of the migrationsource as a new LDEV number (VDEV number) 8011 on the LDEV number (VDEVnumber) 8011 of the migration destination in the Address Map ManagementTable 801, as shown in FIG. 22B.

Then, for example, as shown in FIG. 17, when the NAS node 10 receives afile read request designating the file that has been stored in thevirtual internal LDEV #2 from the client 301, the NAS node 10 transmitsthe block read request designating the virtual internal LDEV #2 and theaccess destination address thereof to the primary storage system 600.The LDEV Management Table 803 and the Address Map Management Table 801are such as shown by way of an example in FIG. 22A, and FIG. 22B,respectively. Further, in the Extent Management Table 861 thatcorresponds to the virtual internal LDEV #2, the change flag 8615corresponding to this access destination address becomes “On”, the VDEVnumber 8617 becomes the VDEV number of the virtual internal LDEV #1, anda corresponding extent ID 8616 is present in the access destinationaddress. An address 8612 is specified from a record in which thecorresponding extent ID 8616 of the Extent Management Table 861corresponding to the virtual internal LDEV #1 has been recorded as theID 8611. Therefore, the Program 707 of Access Control can read data froma position corresponding to the specified address 8612 of the externalLDEV corresponding to the virtual internal LDEV #1 according to theblock read request received from the NAS node 10 and can transmit thedata to the NAS node 10. In other words, in the case where a file inwhich a file body is present in the external LDEV corresponding to theinternal LDEV #1, this file being located in the internal LDEV #2, isdesignated as an access destination, the external LDEV corresponding tothe internal LDEV #2 is not accessed, but the external LDEVcorresponding to the internal LDEV #1 is accessed by the ExtentManagement Table 861 or Address Map Management Table 801 correspondingto the internal LDEV #2, #1 (in other words, the access path ischanged).

Further, the access attribution 8613 “Read Only” is associated with theaddress 8612 described in the Extent Management Table 861 correspondingto the virtual internal LDEV #1, #2. Therefore, the migrated data cannotbe written, but the access attribution 8034 of the virtual internal LDEV#1, #2 becomes “Read/Write”. Therefore, the data can be written intopositions other than the positions where the migrated data have beenstored. In other words, before the migration, the access attribution“Read Only” is set in the internal LDEV units, but after the migration,the access attribution “Read Only” is set in file units. For example, inthe case where only a file with a file name “file1.txt” is designated asan archive object and an archive indication is issued in the GUI shownin FIG. 18A and displayed by the Utility Program 715 and then amigration is performed with respect to this file, the access attributionof this file becomes “Read Only” in the migration destination, asrepresented by the GUI of FIG. 18B.

The first embodiment was explained above.

As for the hash value recorded in the Contents Identifier ManagementTable 835, when the archive object is designated in file units, the hashvalue of the designated file is recorded, and when the archive object isdesignated in directory units, the hash value of each file located inthe designated directory is recorded. The data that will be migratedalso can be made a file designated as an archive object (or a file in adirectory designated as an archive object).

Further, the Program 701 of Migration Execution can report as an actualtransition object data quantity a value obtained by subtracting thecapacity of a block section (for example, a product of a block length512 byte and the number of blocks) specified from the address 8612corresponding to the change flag 8615 “On” in the Extent ManagementTable 861 corresponding to the internal LDEV #1, #2 from the transitionobject data quantity, as shown in FIG. 17. More specifically, forexample, if a first file is deleted when the access destination of thefirst file is changed to the second file, the saved storage capacity maybe calculated based on the number of blocks where the body of the firstfile was stored. Further, for example, if the first file is processed byreplacing with a link, the saved storage capacity may be calculatedbased on the value obtained by subtracting the number of blocks thatstore the information of the replaced link from the number of blocksstoring the body of the first file.

Further, for example, the Utility Program 715 may be executed by the NASnode 10. The Utility Program 715 may save the Contents IdentifierManagement Table 835 of each internal LDEV of the archive indicationobject in storage resources of the NAS node 10. When read access to acertain file is executed, the Utility Program 715 or the Program 705 ofDetermination Control compares the hash value 8351 present in theContents Identifier Management Table 835 saved by the Utility Program715 and located in the hash record corresponding to the file of thisread object with the hash value 8351 on the hash record corresponding tothe file of the read object in the Contents Identifier Management Table835 that has been stored in the storage resources of the primary storagesystem 600, and if the two hash values are the same, the program decidesthat the contents of the file of the read object is correct and readsthe file, whereas if the two hash values differ from each other, theprogram may decide that the contents of the file of the read object isincorrect and may return the determination results to the read accesssource. Further, the above-described comparison and determination may beexecuted at the predetermined timing, for example, in the case where thestorage period limit of the file is shorter than the predeterminedperiod, instead of reading.

In accordance with the above-described first embodiment, the presence ofduplicate files in a plurality of files that are the archive objects isdetermined and when the duplicate files are found, at least one of theduplicate files is left and at least one of the duplicate files iseliminated. However, in the NAS node 10, the duplicate files appear tobe present unchanged. The access destination of the eliminated file isassociated with the access destination of the body of the remaining fileby updating the information stored in the Extent Management Table 861and Address Map Management Table 801. As a result, it becomesunnecessary to use the hash value itself for the file address and,therefore, no special API has to be provided in the NAS node 10.

Further, according to the first embodiment, the information relating tothe repository of files such as access attribution relating to the filesstored in the secondary storage system 40 is collected in the primarystorage system 600. As a result, when the number of files that are thearchive objects increases and the information capacity is wished to beincreased, the secondary storage system 40 may be enlarged as a storagesystem for the archive. Thus, it is not necessary to introduce a devicehaving special functions when the information capacity for the archiveis increased, and the storage system of the already existing product canbe effectively used.

Further, according to the first embodiment, when an archive indicationis issued, migration is performed from the real internal LDEV 31 intothe virtual internal LDEV 132, and then the port number 8031, LUN 8032,and LDEV number 8033 of the migration source and the port number 8031,LUN 8032, and LDEV number 8033 of the migration destination areexchanged. Therefore, even after the migration of files that are thearchive objects, the NAS node 10 can acquire the data identical to thosebefore the migration if the location identical to that before themigration is indicated, without being aware of the migrationdestination.

Second Embodiment

The second embodiment of the present invention will be described below.The difference between the first and second embodiment will be mainlydescribed below and the explanation of common features of the twoembodiments will be omitted or simplified.

For example, it will be assumed that a plurality of external LDEV arepresent in one or a plurality of secondary storage systems 40, and thatthe plurality of external LDEV have different characteristics (referredto hereinbelow as “external LDEV characteristics”). The external LDEVcharacteristics differ depending on the type of external storage device(for example, an external disk 500) used to prepare the external LDEV.For example, at least one characteristic from among performance (forexample, transfer speed), reliability, cost, and storage device type(for example, a hard disk or a flash memory) can be used as the externalLDEV characteristic. More specifically, for example, if the externalstorage device has a high speed and high reliability, the external LDEVcharacteristics of the external LDEV prepared by using the externalstorage device will be a high-speed and high-reliability characteristic.Furthermore, for example, if the external storage device has a low speedand low cost, the external LDEV characteristics of the external LDEVprepared by using the external storage device will be a low-speed andlow-cost characteristic. In the explanation below, it will be assumedthat there are first to third external LDEV corresponding to the firstto third virtual internal LDEV, respectively, and that the external LDEVcharacteristic of the first external LDEV is a high-speed andhigh-reliability characteristic, whereas the external LDEVcharacteristics of the second and third external LDEV are low-speed andlow-cost characteristics. Further, it is assumed that three duplicatefiles (first to third files) will be migrated into the first to thirdvirtual internal LDEV, respectively. However, whether actual migrationis performed (in other words, whether data (body) of a file are writteninto the external LDEV) will be controlled by the below-describedelimination determination criterion. Further, in the explanation below,a long or short storage period limit 8614 means that the term indicatedby the storage period limit 8614 is long (in other words, farther in thefuture) or short, respectively.

As shown in FIG. 19A, in the first embodiment, the storage period limit8614 of a file is the only criterion (referred to hereinbelow as“elimination determination criterion”) for determining which file bodyfrom among the duplicate files will be left and which file body will beeliminated (for example, deleted or replaced with a link). For thisreason, for example, if the first storage period limit 8614 is thelongest of the three duplicate files as in Case 1, the first file iswritten into the first external LDEV, and the second and third files arenot written into the second and third external LDEV. As a result, thebodies of the three duplicate files are saved in the first external LDEV(high-speed and high-reliability external LDEV) at least until the firststorage period limit 8614 is reached. However, if the third storageperiod limit 8614 is the longest of the three duplicate files as in Case2, the bodies of the three duplicate files are saved in the thirdexternal LDEV (low-speed and low-reliability external LDEV). For thisreason, the body of the file that has to be saved until the longestperiod limit is reached, will be saved continuously in the low-speed andlow-cost external LDEV.

Accordingly, as shown in FIG. 19B, in the second embodiment, an externalLDEV characteristic is also used in addition to the storage period limit8614 as the elimination determination criterion. More specifically, forexample, as shown in FIG. 20, an external LDEV characteristic 8014 canbe recorded in each record of an Address Map Management Table 801′ andby referring to the Table 801′ it can be possible to specify whichvirtual internal LDEV is associated with which externally LDEV havingany characteristic external LDEV. As shown in FIG. 19B, in Case 1, thestorage period limit 8614 of the first file is the longest and the firstfile is migrated into the first virtual internal LDEV. Therefore,eventually, the bodies of the three duplicate files are written onlyinto the first external LDEV in the same manner as in FIG. 19A. However,for example, in Case 2, the third storage period limit 8614 is thelongest, and in the third file the storage period limit 8614 thereof isthe longest. Therefore, the body of the third file is written into thethird external LDEV, while the body of the first file is written intothe first external LDEV by taking into consideration that the migrationdestination thereof corresponds to the high-speed and high-reliabilityexternal LDEV. Further, because the storage period limit 8614 of thesecond file is the shortest, the body is eliminated and an access changecontrol is performed so as to access any one of the body of the firstfile and the body of the third file. As for which of the files will beaccessed, the body of the third file with the longest storage periodlimit 8614 may be accessed, but with consideration for the accesscompetition, the body of the first file may be also accessed, as shownin FIG. 19B. Further, in the case where the body of the first filecannot be acquired, for example, because failure has occurred in thefirst external LDEV, the Extent Management Table 861 may be updated inorder to change the access destination of the first and second files tothe third file. The impossibility of referring to the file can thus beavoided.

An example of the address control processing flow of the secondembodiment is shown in FIG. 21.

The Program 705 of Determination Control refers to all the ContentsIdentifier Management Tables 835 corresponding to all the internal LDEVof the archive object and retrieves two or more identical hash values8351 (S51). If such hash values 8351 are not found, the processing maybe completed.

If the external LDEV attribution 8014 has not been associated (S52: NO)with at least one or all the virtual internal LDEV from among one ormore virtual internal LDEV that are the migration destinations of aplurality of files corresponding to at least two identical hash values8351, the Program 705 of Determination Control advances to step S61, andif the external LDEV attribution 8014 has been associated with these oneor more virtual internal LDEV (552: YES), the program advances to S54 orS56.

In S61, the Program 705 of Determination Control selects the longeststorage period limit 8614 from among a plurality of storage periodlimits 8614 of files corresponding to two or more identical hash values8351. More specifically, for example, the change flag 8615 correspondingto a hash value 8351 with a shorter storage period limit 8614 from amongthe matching hash value and the selected hash value 8351 from among twoor more identical hash values 8351 is set to “On”, the extent ID 8616 isupdated, and if necessary, a VDEV number 8617 is updated. This isexecuted by the Program 705 of Determination Control by taking each oftwo or more identical hash values 8351 as the selected hash values 8351.As a result, if there is only one longest storage period limit 8614 in aplurality of files corresponding to two or more identical hash values8351, this storage period limit 8614 is selected and the processing flowadvances to S62. If a plurality of the longest storage period limits8614 (in other words, identical storage period limits 8614) are present,as shown in step S70 in FIG. 21, the Program 705 of DeterminationControl selects the storage period limit 8614 with a large number ofchange flags 8615 “On” (that is, the storage period limit 8614corresponding to the file in which a large number of address changedestinations are present) as the longest storage period limit 8614. Ifthe number of change flags 8615 “On” is the same, the Program 705 ofDetermination Control selects one storage period limit 8614 that wasselected arbitrarily (for example, a storage period limit 8614 of acomparative source) as the longest storage period limit 8614.

In step S62, the Program 705 of Determination Control updates eachExtent Management Table 861 so as to access a file corresponding to thestorage period limit 8614 having selected therefor in S61 at least onefile corresponding to the storage period limit 8614 that was notselected in S61. More specifically, the Program 705 of DeterminationControl sets to “On” the change flag 8615 corresponding to unselectedanother storage period limit 8614, without changing the “Off” state ofthe change flag 8615 corresponding to the selected storage period limit8614. The Program 705 of Determination Control changes the extent ID8616 corresponding to “On” of the change flag 8615 to ID 8611 on therecord corresponding to the selected storage period limit 8614. Further,the Program 705 of Determination Control updates, as necessary, the VDEVnumber 8167 corresponding to the change flag 8615 “On”.

A case in which all the external LDEV 8014 characteristics associatedwith one or more internal LDEV are “high speed and high reliability” isa case in which the processing flow advances to S54 after YES in S52. Acase in which “high speed and high reliability” is mixed with “low speedand low cost” in these one or more external LDEV characteristics 8014 isa case in which the processing flow advances to S56.

In S54, the Program 705 of Determination Control selects the longeststorage period limit 8614 from among the storage period limits 8614 of aplurality of files (a plurality of files corresponding to “high speedand high reliability”) corresponding to two or more identical hashvalues 8351. If there are a plurality of the longest storage periodlimits 8614 (in other words, identical storage period limits 8614), theprocessing flow advances to S70 of FIG. 21.

In S55, the Program 705 of Determination Control updates the ExtentManagement Table 861 so as to access a file corresponding to the storageperiod limit 8614 having selected therefor in S54 one or more filescorresponding to the storage period limits 8614 that was not selected inS54.

In S56, the Program 705 of Determination Control selects the longeststorage period limit 8614 from among one or more storage period limits8614 corresponding to the external LDEV characteristic 8014 “lowspeed-low cost” from among the storage period limits 8614 of a pluralityof files corresponding to two or more identical hash values 8351. Ifthere are a plurality of the longest storage period limits 8614 (inother words, identical storage period limits 8614), the processing flowadvances to S70 of FIG. 21. Further, in this step S56, the longeststorage period limit 8614 may be also selected from one or more storageperiod limits 8614 corresponding to “high speed and high reliability”.

In S57, the Program 705 of Determination Control compares the longeststorage period limits 8614 that was selected for “high speed and highreliability” (referred to hereinbelow as “high-speed term 8614”) withthe longest storage period limits 8614 that was selected for “low speedand low cost” (referred to hereinbelow as “low-speed term 8614”).

If the comparison results of S57 demonstrate that the low-speed term8614 is longer than the high-speed term 8614 (558: YES), the Program 705of Determination Control leaves the change flag 8615 corresponding tothe storage period limit 8614 at “Off”, sets the change flag 8615corresponding to other storage period limits 8614 relating to “low speedand low cost” to “On”, and updates the extent ID 8616 corresponding toother storage period limits 8614 so that the access destination of thefile corresponding to the other storage period limit 8614 is a filecorresponding to the high-speed term 8614 (S59).

If the comparison results of S57 demonstrate that the low-speed term8614 is less than the high-speed term 8614 (S58: NO), the Program 705 ofDetermination Control sets the change flag 8615 corresponding to thelow-speed term 8614 and the change flag 8615 corresponding to the otherstorage period limit 8614 relating to “low speed and low cost” to “On”and updates the extent ID 8616 and the like corresponding to all thesefiles so that access destination of all the files relating to “low speedand low cost” is set to a file corresponding to the high-speed term 8614(S60).

Several embodiments of the present invention are described above, butthey are merely examples illustrating the present invention, and thescope of the present invention is not limited to these embodiments. Thepresent invention can be also carried out in a variety of other modes.For example, the Utility Program 715 may be in the NAS node 10 and maybe in the primary storage system 600. Further, the file systemmanagement information (information shown by way of an example in FIG.5) that is used by the NAS node 10 may be stored in the storageresources (for example, internal LDEV) located in the primary storagesystem 600. Furthermore, for example, the NAS node 10 and/or themanagement terminal 106 may be contained in the primary storage system600. Furthermore, for example, when a plurality of files are duplicatedin a virtual LDEV, but one or more certain files from among theseplurality files are stored in an external LDEV and files other than theone or more certain files from among these plurality of files (referredto hereinbelow as “other files”) are not stored in the external LDEV,the storage area in the external LDEV corresponding to the storage areain which the other files are present in the virtual LDEV becomesunoccupied storage area, and this unoccupied storage area may be alsoused (for example, any information may be stored in the unoccupiedstorage area).

What is claimed is:
 1. A computer system comprising: a computer; and afirst storage system having one or more first logical storage deviceswhere a plurality of files are stored, a second storage system havingone or more second logical storage devices, wherein said computerincludes: a hash value calculation unit that calculates a plurality ofhash values that are values intrinsic to contents of a plurality offiles, respectively; and a hash value transmission unit that transmits aplurality of hash values corresponding respectively to said plurality offiles to said first storage system, and said first storage systemincludes: a duplication determination unit that determines whether twoor more identical hash values are contained in said plurality of hashvalues; and a change control unit that changes an access destination ofa first file corresponding to a first hash value from among these two ormore identical hash values, to a position having stored therein a secondfile corresponding to a second hash value from among these two or moreidentical hash values when there are said two or more identical hashvalues, a migration execution unit which, when the migration executionunit migrates data stored in files stored in said one or more firstlogical storage devices to said one or more second logical storagedevices, does not migrate first data of said first file to any of saidone or more second logical storage devices, and migrates second data ofsaid second file to any of said one or more second logical storagedevices.
 2. The computer system according to claim 1, wherein there area plurality of storage period limits that are respectively associatedwith said plurality of hash values, and said change control unit changesan access destination of said first file corresponding to said firststorage period limit to a position having stored therein said secondfile corresponding to a second storage period limit that is longer thanthe first storage period unit, from among two or more storage periodlimits respectively corresponding to said two or more identical hashvalues.
 3. The computer system according to claim 1, wherein said firststorage system further comprises: one or more virtual logical storagedevices respectively associated with said one or more second logicalstorage devices; and a migration execution unit that writes a body ofeach file stored in said one or more first logical storage devices tosaid one or more second logical storage devices via said one or morevirtual logical storage devices of a migration destination, and whereinsaid migration execution unit does not write a body of said first fileinto any of said one or more second logical storage devices and writes abody of said second file into any of said one or more second logicalstorage devices from among two or more files respectively correspondingto said two or more identical hash values, and said change control unitchanges an access destination of said first file to a position where abody of said second file has been written.
 4. The computer systemaccording to claim 3, wherein before said migration is started, none ofsaid one or more first logical storage devices that store said pluralityof files can be updated, and after said migration is completed, each ofsaid one or more virtual logical storage devices can be updated, butnone of said plurality of files that have become the object of saidmigration can be updated.
 5. The computer system according to claim 3,wherein there are a plurality of storage period limits respectivelyassociated with said plurality of hash values, and said change controlunit changes an access destination of said first file corresponding tosaid first storage period limit to a position having stored therein saidsecond file corresponding to a second storage period limit that islonger than the first storage period unit, from among two or morestorage period limits respectively corresponding to said two or moreidentical hash values.
 6. The computer system according to claim 5,wherein said change control unit controls the change of accessdestination based on a device characteristic of said one or more secondlogical storage devices.
 7. A storage control method effected via acomputer system which includes: a computer; and a first storage systemhaving one or more first logical storage devices where a plurality offiles are stored, a second storage system having one or more secondlogical storage devices, wherein said storage control method comprising:said computer effecting operations of: calculating a plurality of hashvalues that are values intrinsic to contents of a plurality of files,respectively; and transmitting a plurality of hash values correspondingrespectively to said plurality of files to said first storage system,and said first storage system effecting operations of: performingduplication determination by determining whether two or more identicalhash values are contained in said plurality of hash values; and changingan access destination of a first file corresponding to a first hashvalue from among these two or more identical hash values, to a positionhaving stored therein a second file corresponding to a second hash valuefrom among these two or more identical hash values when there are saidtwo or more identical hash values, migrating data stored in files storedin said one or more first logical storage devices to said one or moresecond logical storage devices, by not migrating first data of saidfirst file to any of said one or more second logical storage devices,and migrating second data of said second file to any of said one or moresecond logical storage devices.
 8. The storage control method accordingto claim 7, further comprising: associating a plurality of storageperiod limits that are with said plurality of hash values respectively,and effecting an operation of changing an access destination of saidfirst file corresponding to said first storage period limit to aposition having stored therein said second file corresponding to asecond storage period limit that is longer than the first storage periodunit, from among two or more storage period limits respectivelycorresponding to said two or more identical hash values.
 9. The storagecontrol method according to claim 7, wherein said first storage systemfurther includes: one or more virtual logical storage devicesrespectively associated with said one or more second logical storagedevices; and wherein said storage control method further effectingoperations of: writing a body of each file stored in said one or morefirst logical storage devices to said one or more second logical storagedevices via said one or more virtual logical storage devices of amigration destination, and said migrating does not write a body of saidfirst file into any of said one or more second logical storage devicesand writes a body of said second file into any of said one or moresecond logical storage devices from among two or more files respectivelycorresponding to said two or more identical hash values, and changing anaccess destination of said first file to a position where a body of saidsecond file has been written.
 10. The storage control method accordingto claim 9, wherein before said migrating is started, none of said oneor more first logical storage devices that store said plurality of filescan be updated, and after said migrating is completed, each of said oneor more virtual logical storage devices can be updated, but none of saidplurality of files that have become the object of said migration can beupdated.
 11. The storage control method according to claim 9,comprising: associating a plurality of storage period limits that arewith said plurality of hash values, respectively, and effecting anoperation of changing an access destination of said first filecorresponding to said first storage period limit to a position havingstored therein said second file corresponding to a second storage periodlimit that is longer than the first storage period unit, from among twoor more storage period limits respectively corresponding to said two ormore identical hash values.
 12. The storage control method according toclaim 11, comprising controlling the change of access destination basedon a device characteristic of said one or more second logical storagedevices.
 13. A non-transitory computer-readable medium embodying astorage control method effected via a computer system which includes: acomputer; and a first storage system having one or more first logicalstorage devices where a plurality of files are stored, a second storagesystem having one or more second logical storage devices, wherein saidstorage control method comprising: said computer effecting operationsof: calculating a plurality of hash values that are values intrinsic tocontents of a plurality of files, respectively; and transmitting aplurality of hash values corresponding respectively to said plurality offiles to said first storage system, and said first storage systemeffecting operations of: performing duplication determination bydetermining whether two or more identical hash values are contained insaid plurality of hash values; and changing an access destination of afirst file corresponding to a first hash value from among these two ormore identical hash values, to a position having stored therein a secondfile corresponding to a second hash value from among these two or moreidentical hash values when there are said two or more identical hashvalues, migrating data stored in files stored in said one or more firstlogical storage devices to said one or more second logical storagedevices, by not migrating first data of said first file to any of saidone or more second logical storage devices, and migrating second data ofsaid second file to any of said one or more second logical storagedevices.
 14. The non-transitory computer-readable medium according toclaim 13, wherein said storage control method comprising: associating aplurality of storage period limits that are with said plurality of hashvalues, respectively, and effecting an operation of changing an accessdestination of said first file corresponding to said first storageperiod limit to a position having stored therein said second filecorresponding to a second storage period limit that is longer than thefirst storage period unit, from among two or more storage period limitsrespectively corresponding to said two or more identical hash values.15. The non-transitory computer-readable medium according to claim 13,wherein said first storage system further includes: one or more virtuallogical storage devices respectively associated with said one or moresecond logical storage devices; and wherein said storage control methodfurther effecting operations of: writing a body of each file stored insaid one or more first logical storage devices to said one or moresecond logical storage devices via said one or more virtual logicalstorage devices of a migration destination, and said migrating does notwrite a body of said first file into any of said one or more secondlogical storage devices and writes a body of said second file into anyof said one or more second logical storage devices from among two ormore files respectively corresponding to said two or more identical hashvalues, and changing an access destination of said first file to aposition where a body of said second file has been written.
 16. Thenon-transitory computer-readable medium according to claim 15, whereinbefore said migrating is started, none of said one or more first logicalstorage devices that store said plurality of files can be updated, andafter said migrating is completed, each of said one or more virtuallogical storage devices can be updated, but none of said plurality offiles that have become the object of said migration can be updated. 17.The non-transitory computer-readable medium according to claim 15,wherein said storage control method further effecting operations of:associating a plurality of storage period limits that are with saidplurality of hash values, respectively, and effecting an operation ofchanging an access destination of said first file corresponding to saidfirst storage period limit to a position having stored therein saidsecond file corresponding to a second storage period limit that islonger than the first storage period unit, from among two or morestorage period limits respectively corresponding to said two or moreidentical hash values.
 18. The non-transitory computer-readable mediumaccording to claim 17, wherein said storage control method furthereffecting operations of: controlling the change of access destinationbased on a device characteristic of said one or more second logicalstorage devices.